feat: deploy solar-ui as part of the solar chart - #743

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands.}

Otherwise LGTM

Only nitpicks e.g. two tiny things beyond the inline suggestions

* `ui.args.authMode` is the only key under `args`, while `extraArgs` sits right next to it as a sibling. Reads a bit odd, you'd maybe expect `ui.authMode` directly, or `extraArgs` nested under `args`. Pure naming, not important.

* `ui.imagePullSecrets` doc is terser than the siblings (renderer spells out the `[{name: my-secret}]` shape). Could mirror that one-liner so the value docs stay uniform, up to you 🤷

good point, i looked into it: both these point would make the ui section more inconsistent with the rest of the file:
the args, exraArgs split is convention, applied that way in other sections of the chart as well. This also mirrors the python *args, **kwargs pattern (which is why its often used elsewhere) so at least to me not splitting it would read a bit odd to me 😅
as for having it under ui.authMode: the args block, even if it only holds a single item (for now) is what's passed onto the cli call as args for the bff. THe block serves a purpose in that way, i'd prefer to keep it as is.

as for the pullSecrets: renderer is actually the outlier, ui is consistent with apiserver and controller. Renderer looks slightly different because the pod runs in the rt's namespace, so the secret has to exist in multiple namespaces